Tracking Code Manager Security Vulnerabilities and Issues — Tracking Code Manager CVE List

Lucene search

Data443Tracking Code Manager

5 matches found

CVE•added 2024/03/21 5:15 p.m.•45 views

CVE-2024-2579

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Data443 Tracking Code Manager.This issue affects Tracking Code Manager: from n/a through 2.0.16.

5.9CVSS6.2AI score0.00091EPSS

CVE•added 2025/01/30 6:15 a.m.•40 views

CVE-2024-10309

The Tracking Code Manager WordPress plugin before 2.4.0 does not sanitise and escape some of its metabox settings when outputing them in the page, which could allow users with a role as low as Contributor to perform Cross-Site Scripting attacks.

5.9CVSS5.6AI score0.0004EPSS

CVE•added 2024/12/24 10:15 a.m.•35 views

CVE-2024-8721

The Tracking Code Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the tracking code field in all versions up to, and including, 2.3.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level ...

6.4CVSS6.1AI score0.00037EPSS

CVE•added 2024/06/09 6:15 p.m.•34 views

CVE-2024-31347

Missing Authorization vulnerability in Data443 Tracking Code Manager.This issue affects Tracking Code Manager: from n/a through 2.1.0.

4.3CVSS4.8AI score0.0011EPSS

CVE•added 2025/05/15 8:15 p.m.•17 views

CVE-2024-6335

The Tracking Code Manager WordPress plugin before 2.3.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup)

4.8CVSS5.6AI score0.00039EPSS